An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, I'm submitting my watchOS-only app and its In-App Purchase for the very first time (both app and IAP submitted simultaneously). After multiple rejections, I still can't resolve the issue and would appreciate any guidance. Environment: App type: watchOS-only (no iOS companion app) First submission of both the app and IAP IAP type: Non-Consumable, Product Apple ID: 6770497337 The problem: The reviewer (App Review) states that the IAP product information cannot be retrieved in the review environment. According to the reviewer, they are testing in the production environment, not the sandbox. However: In my TestFlight build, the app correctly retrieves the IAP product I have successfully completed the full purchase flow using a sandbox account All business agreements (including Paid Apps Agreement) are accepted and active in The Bundle ID and Product ID are correctly configured in both Xcode and App Store Connect Current IAP status in App Store Connect: Overall status: "Developer Action Needed" All localizations (English US/UK/AU/CA, Japanese, Simplified Chinese, Traditional Chinese): "Rejected" No specific rejection reason is shown anywhere in App Store Connect Any help would be greatly appreciated. Thank you! 🙏

Hi, My app (6766506951) has been in review for two weeks with no status update. I already emailed the App Review team and submitted an expedited review request last week, but I haven’t received any response and the status is still “Waiting for Review.” I’m not sure what else I should do at this point. I would really appreciate your help.

My app has been stuck in the “Waiting for Review” stage for the past 9 days, and I have not received any updates, feedback, or rejection notices. I have already contacted support multiple times regarding this issue, but unfortunately I have not received a response yet. I have spent a significant amount of time and resources building this app, including purchasing the required Apple Developer subscription and preparing everything according to the App Store guidelines. I kindly request you to please check my submission status or let me know if there is any issue causing the delay. Even a small update would be greatly appreciated. Case ID: 102893147964

Hello, I’m looking for guidance on a first auto-renewable subscription review issue that appears to be stuck. Our app “Skinora: AI Skincare Routine” has already been approved and is live on the App Store, but both of our first auto-renewable subscriptions are still stuck in “In Review”. App version: 1.0.1 Build: 6 Subscriptions: Skinora Pro Annual — product ID: skinora_pro_annual Skinora Pro Weekly — product ID: skinora_pro_weekly_Access Current App Store Connect state: App version 1.0.1 is approved/live Subscription group localization is Approved Both subscription products still show In Review There are no visible Resolution Center messages or Notes from App Review requiring action from us Background: The subscriptions were originally returned because the first subscriptions needed to be submitted with a new app version/binary. We then submitted them together with app version 1.0.1 build 6. The app was approved, but the subscriptions have remained In Review for several working days. (8 days) This is blocking our launch because the live app depends on these subscriptions for Pro access, and users cannot purchase/unlock Pro until Apple approves the products. I have already contacted Apple Developer Support multiple times and also called support. The support representative said they would escalate it internally, but the status has not changed yet. Is this a known App Store Connect issue with first auto-renewable subscriptions? Is there any way to confirm whether the subscriptions are actually being reviewed or stuck in an inconsistent state? Should I continue waiting, or is there a specific action needed to reset or move the subscription review forward? Any guidance would be appreciated.

Hello App Review team - I am an iOS developer and my app(App ID: 6756242440) is stuck in 'Waiting for review'. Please help us resolve the issue. Thanks in advance!

Hello, respected Apple Developer Forums community. SKU: com.apatura.safenet Apple ID: 6762392582 I am writing here because for almost a month we have not been able to find a solution to the situation with publishing our app, and I sincerely hope to get advice from other developers or Apple representatives. We are developing a VPN service. Initially, at an early stage, we tried to submit the app to the App Store from an individual Apple Developer account. Later, we understood that for this type of service we should use an organization account. Over time, the old Xcode project was lost. Because of that, we created a new project with the same name and similar visual materials, and submitted the app from the organization account. After that, the app was rejected under Guideline 4.3(a) — Design: Spam. The App Review message says that the app shares a similar binary, metadata, and/or concept with apps submitted to the App Store by other developers. We assume that the system may have linked the current submission to our previous submission from the individual account. It was in fact our own project, not an attempt to create a duplicate. We already explained this to the App Review Team in App Store Connect and provided information about the previous submission. We were even able to completely remove that app from App Store Connect under the individual account. We also explained that the current submission is being made from the organization account. After that, App Review requested additional information about the VPN functionality: what data the app collects, why it is used, and whether it is shared with third parties. We answered this in detail. However, after that we received the same rejection again under Guideline 4.3(a) — Design: Spam, without any additional explanation of what exactly we need to fix. We tried once again to explain that this is not spam and not a duplicate of someone else’s app. We also removed the old app record from the individual account so that it could no longer create a conflict or be detected as a possible duplicate. Now we are in a very difficult situation. We are not trying to bypass the rules. We are not publishing a network of identical apps. We are not using someone else’s template, and we are not trying to clutter the App Store. This is one real VPN service that we want to publish on behalf of the organization that operates it. It is very difficult when you wait several weeks for review, answer questions in detail, explain the situation, but then receive the same generic response again without understanding what exactly is wrong and what specifically needs to be done. We truly want to resolve this situation correctly, without conflict and without violating the rules. We just need a clear path forward. Apple Review Team, please read our thread in App Store Connect before replying with the same response again without real attention to the issue. I would be very grateful for any help, advice, or experience from developers who have faced a similar situation. With each new review, we wait 7–10 days and then receive the same generic replies without any real engagement. Thank you.

As a game studio with real business commitments, we depend on a predictable App Review process. Every month, we publish updates, run user acquisition campaigns, and test new ideas; that’s how our business operates. It’s not optional. We have obligations to our partners, our marketing budgets are committed in advance, and our entire monthly rhythm depends on getting builds out on schedule. Right now, Apple’s App Review is making that impossible. For the past 30 days, we’ve been stuck in a rejection loop on a single submission. Here’s what the cycle looks like: • Apple rejects our build with vague, generic feedback that doesn’t actually identify what’s wrong. • We investigate every possible scenario that could conceivably match their description, fix what we believe is the issue, and resubmit, usually within three hours. • Then we wait. And wait. Each review of the resubmission takes more than ten days. Read that again: we respond in 3 hours, they respond in 2 weeks. This isn’t a one-off. It’s been three full cycles now, and we still don’t have clarity on what they actually want changed. The rejection notes are so shallow that we’re forced to guess; patch a plausible cause, ship it, and hope. It honestly feels like reviews are being triaged by AI models that aren’t ready for the job yet: surface-level pattern matching, no real engagement with the build, no specifics we can act on. Meanwhile, the cost is real: • UA campaigns we’ve already committed budget to are bleeding out. • Partner deliverables are slipping. • Our team’s monthly release rhythm — the engine of how we operate as a business — is broken. • We’re paying engineers to play guessing games with a reviewer who won’t tell us what’s wrong. We’ve escalated everywhere we can. Contact forms, appeals, developer support, every channel Apple offers. Nothing has moved. We love the platform. We want to keep shipping great games on iOS. But Apple needs to understand that App Review isn’t just a gatekeeping checkbox, it’s a load-bearing piece of every developer’s business operation. When a single rejection cycle eats 10+ days and the feedback isn’t actionable, you’re not protecting users. You’re breaking the businesses building for your platform. Two things need to change, urgently: 1. Restore meaningful, specific rejection feedback. Tell us exactly what’s wrong, with reproduction steps. If a human reviewer can’t be specific, an AI definitely shouldn’t be making the call. 2. Prioritize resubmissions on an in-flight review. A 10-day turnaround on a fix to a rejection you issued, three hours earlier, is indefensible. These should jump the queue, not start at the back. If anyone at Apple is reading this: we’re trying to work with you. Please help us help you. Want me to tighten it, make it angrier, soften it, or pull out the bullet lists so it reads as straight prose for the forum?

I want to share how I truly feel about this situation. I have spent years building every single app on my account before publishing anything on the App Store. Each one represents months of work, testing, and genuine effort to create something valuable for users. I am proud of what I built and I stand behind every app I have ever submitted. I honestly do not believe I deserve this decision. I have never intentionally violated any guideline. I have never tried to deceive Apple or users. I have always engaged with the review process in good faith, even when it was difficult and took months. The notice itself states that automation may have been used as part of the review process. I strongly believe this was an automated mistake. A human reviewer who looks carefully at my submission history and my apps will not find evidence of concept switching or hidden features; because there is none. I am a student in France. This account is how I support myself. Losing it overnight, after years of work, without a proper human review, is devastating. I am not asking for special treatment. I am asking for a fair human review of my case before a final decision is made. Thank you for reading this.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { "errors": [{ "id": "80550434-590c-48c6-b2d3-5bd3b038539b", "status": "409", "code": "ENTITY_ERROR.RELATIONSHIP.INVALID", "title": "The provided entity includes a relationship with an invalid value", "detail": "The specified pre-release build could not be added.", "source": { "pointer": "/data/relationships/build" } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5​-2671​-44d6​-bacb​-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuck? The builds show as valid in TestFlight but cannot be attached to the App Store version.

My app ActLike AI – Face Swap Video (Apple ID: 6761327996, Bundle ID: com.LCDMediaGames.ActLike-AI) has been stuck in “Waiting for Review” for almost two weeks. Normally, my app submissions move from “Waiting for Review” to “In Review” within 2–3 days. However, this submission has not started review yet. I have already tried the following: Contacted Apple Developer Support Called support Submitted an expedited review request Removed and resubmitted the build Unfortunately, the app is still stuck in “Waiting for Review”. This delay is affecting my release schedule and causing unnecessary backend/infrastructure costs because the app uses AI video generation services. Could someone from Apple please check whether this submission is blocked, delayed, or requires any action from my side? Any help would be appreciated.

My app SoulPal: AI Social Media (Apple ID: 6765955053) has been stuck in review since Friday. This is my second submission after addressing all rejection feedback immediately. I have submitted a Contact Us request but received no response. Every day without a resolution is adding unnecessary infrastructure costs. Any help would be appreciated.

Hello, My app Wecheerup 360 Booth (App ID: 676214516, bundle ID: com.wecheerup.wecheerup360booth.ios) has been stuck in the App Review process for longer than expected. Version 1.0.3 was submitted on April 13, 2026 and has been in “In Review” status for over 15 days. There are no messages in the Resolution Center and all metadata appears to be complete on my side.

To the Apple Review and Developer Support Teams, I am writing to request guidance and assistance regarding a persistent rejection my React Native application is facing under Guideline 2.1 - Performance (In-App Purchases). My app has been rejected multiple times with the following specific note: "The In-App Purchase products in the app still exhibited one or more bugs which create a poor user experience. Specifically, the subscription screen failed to load any subscription plans. Review the details and resources below to troubleshoot this issue." The screenshot provided by the review team shows a completely black screen where our paywall options are intended to populate, indicating that the product array is returning completely empty during the review process. The Dilemma: We are completely unable to reproduce this behavior on our end. Everything functions flawlessly within our TestFlight builds across multiple physical test devices and various sandbox tester accounts. On TestFlight, the paywall renders instantly, local pricing fetches immediately via SKProductsRequest, and test transactions process without a single error. Our Current Implementation & Verification: Product Status: All subscription products are explicitly marked as "Waiting for Review" in App Store Connect with one In-App product Rejected for not being attached with a bin but I've since submitted the app once again. All the subscriptions and the in-app product have been actively attached to this specific app submission version. Agreements: The Paid Apps Agreement is active, signed, and fully up to date within our Agreements, Tax, and Banking configurations. Identifiers: We have strictly verified that the hardcoded product identifiers in our React Native codebase match the App Store Connect product IDs exactly. Because this error only occurs within the App Review environment and never in TestFlight or local sandboxes, we are at a loss for how to debug or resolve this issue. Could the App Review team or the Developer Support technical team please clarify if there is a known environment mismatch, storefront routing discrepancy, or specific network configuration (such as IPv6 handling in the review sandbox) that would cause production-ready StoreKit products to return an empty array exclusively to the reviewer? Any direct guidance, logs, or steps on how we can successfully surface our plans to your review team would be deeply appreciated. Review Environment Submission ID: 5a35279c-1621-4972-b6c6-7c1fb202b2f0 Review date: May 20, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (8) Thank you for your time and assistance.

Dear Apple App Review Team, I hope you are doing well. I am writing to respectfully request assistance regarding my app review status for the following application: App Name: Lang-Talk : Language Lessons App ID: 6761159353 The app was submitted to App Store Connect on March 27, 2026, and it is still showing “Waiting for Review” after more than two months. I previously contacted Apple Developer Support regarding this issue under: Case ID: 102863904030 I received responses on April 15 and April 21 stating that the app was still in the queue and that there was nothing I could do to speed up the process. However, since then, there has been no progress, no review activity, and no additional communication regarding my submission. Because of the unusually long delay, I also posted a question on the Apple Developer Forums to seek guidance from other developers. In my forum post, I explained that: The app has remained in “Waiting for Review” since March 27, 2026 No rejection or feedback has ever been received This is the app’s first submission Many other apps and updates submitted after my app have already been reviewed and released Several developers mentioned that this waiting period is far longer than normal App Store review timelines, which increased my concern that there may be an issue preventing the review process from starting properly. I also submitted an expedite review request, but unfortunately there has been no change in the status. I completely understand that review times may vary depending on internal workload and review requirements. However, after waiting for more than two months without any feedback or status change, I kindly request that the App Review Team please investigate whether there is any hidden issue, account-related problem, or technical reason causing this delay. If any additional information or action is required from my side, I would be happy to provide it immediately. This project is very important to me, and the prolonged uncertainty has become extremely stressful. I would sincerely appreciate any clarification, assistance, or escalation that could help move the review process forward. Thank you very much for your time and support. Kind regards, Sameen Zaka

Hi, My App(6705133649) is in review for a month with no status change. I tired calling the developer team, emailed them and expedited the app review process last week. But no change. I am not sure, what else am i supposed to do. Please help.

Hello everyone, I would like to ask whether other developers are currently experiencing unusually long App Review delays for new apps. Here is the timeline for my app (Apple ID: 6759361892): Build 1 — Feb 19, 2026: Initial build submitted Feb 21, 2026: Rejected because ads were not working properly Build 2 — Feb 23, 2026: Updated build submitted Build 3 — Feb 26, 2026: Another updated build submitted Mar 11–18, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 18, 2026: Submission cancelled and resubmitted Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent several follow-up emails regarding the delay Contacted Apple Support and asked them to leave messages for the App Review team Each time, I was told that the situation would be checked or that the review would “begin shortly.” I have now received that same response multiple times, including after my expedited review request was accepted, but there has still been no visible progress or transition into active review. While browsing the Developer Forums, I also noticed that several recent posts seem to describe similar situations, especially involving new app submissions remaining stuck in “Waiting for Review.” So I would like to ask: Are other developers currently experiencing similar delays? Has anyone recently seen their app finally move from “Waiting for Review” to “In Review” after a very long delay? Could this possibly be related to a broader App Review queue slowdown? I’m mainly trying to understand whether this is an isolated issue or something other developers are also currently facing. Any recent experiences or information would be greatly appreciated. Thank you.

Hi App Review team, My app BadyApp (Badminton Group Management) has been stuck in "Waiting for Review" since May 12, 2026 and has never moved to "In Review" — no reviewer has engaged with it at all. Submission details: App Name: BadyApp Apple ID: 6762489731 Submitted: May 12, 2026 Current status: Waiting for Review (8+ days, no movement) Steps already taken: Submitted Apple Developer Support request at ~80 hours — no response received Resolution Center shows no messages Demo credentials provided in submission Privacy policy URL is active and accessible This is a straightforward badminton group management app with no sensitive permissions. The complete silence — no rejection, no message, no status change — suggests a possible system or queue hold that needs investigation. Could someone from the App Review team please look into this? Happy to provide any additional information. Thank you.

Dear App Review Team, I am writing to follow up again regarding our app review, which has now been pending for over 20 days. App ID: 6705133649 Status: Waiting for Review since April 30, 2026 Despite previous communication indicating that the issue was being investigated and that we would be contacted via App Store Connect, we have still not received any update or outreach. To summarize: April 30 – Submitted for review May 5 – Apple responded that the issue is under investigation Multiple follow-ups since then Today – Over 20 days with no progress, no communication This ongoing delay is significantly impacting our users and business operations. Given that our app reviews were previously completed within 24–48 hours, and considering the extended delay in our last submission as well, we are concerned that there may be an underlying issue affecting our account or app. We kindly request: Immediate escalation to a senior App Review team member A clear explanation for the delay Confirmation if any action is required from our side An estimated timeline for resolution We are fully available to provide any additional information, demo credentials, or clarification needed, and will respond promptly to any requests. We respectfully request that this matter be treated as urgent. Thank you for your attention. Best regards, Bishwajit

My app has been stuck in “Processing for Distribution” for several days. The version was approved, but it never fully completed the distribution process. In App Store Connect, I cannot create a new version because the “+” button is missing. I also cannot submit a new build, update metadata, or cancel the current process. The release pipeline is completely blocked on my side. I contacted Apple Developer Support, and the issue has been escalated to the engineering team under an internal engineering ticket. However, I am still waiting and there is no action available to me in App Store Connect. Has anyone experienced this exact issue before? If so, how long did it take Apple engineering to reset or unblock the app version state?